vkrtandra SonicWall Employee
Comments
-
Hi @Doug_Daniel , The 3 pound characters "###" has special purpose and was designed a long ago (~10+ years) for credential caching. The rational at that time was no one will likely use a password with that combination and has served until now.
-
@Doug_Daniel , the upcoming March 2024 hotfix will have some fixes that you are looking for and will address some of your requests with User VPN.
-
Hi @Doug_Daniel , for the current use-case, there's an easy workaround already available in the client. Please enable "Connect automatically at Windows logon" checkbox under settings. This enables client to continuously probe and connect once the network is UP. This setting can be enabled during install (either from…
-
@Rnnh2023, SEM client and the entire workplace flow including agent activation has been revamped in 12.4.2 release. Agents are auto activated, and users are no longer required to click any button on home page. You may want to upgrade to 12.4.2 and check the new functionality.
-
@Doug_Daniel , this definitely is a bug. If the button got disabled, then I would presume that AlwaysOn VPN checkbox is also enabled in the same user VPN community. Until 12.4.2, enabling AlwaysOn VPN checkbox in the user VPN community triggers a special mode that basically doesn't allow user to disconnect from user VPN…
-
@Doug_Daniel , when you send an API request, make sure that the request contains the name of named pipe for receiving the status from Connect Tunnel client. Here's a simple PS script that spawns a named pipe for receiving status from client. $pipeName = "CTCB" $pipeServer = New-Object…
-
Thanks, @Doug_Daniel , for bringing up the issue. The original intent for not doing aggressive re-connect of User VPN is due to complexity and the side-affects. We allowed only Device VPN to continuously retry for reconnection since it's non-interactive and can reconnect automatically by creating a new session with Device…
-
Please follow the workaround mentioned at https://www.sonicwall.com/support/knowledge-base/sma1000-ct-compatibility-with-3rd-party-vpn-clients-like-gvc-citrix-and-fortinet/220511064616607/.
-
Please follow the workaround listed at https://www.sonicwall.com/support/knowledge-base/sma1000-ct-compatibility-with-3rd-party-vpn-clients-like-gvc-citrix-and-fortinet/220511064616607/.
-
This is a known issue when the client machine has other legacy VPN clients that use DNE. DNE installs legacy filter on all existing adapters, causing Windows adapter configuration API to fail thus leading to CT error. The fix is to disable DNE or uninstall other VPN clients that use DNE.
-
Hi @Chris You can achieve this functionality with Connect Tunnel client in 12.4.1 in 2 ways: In management console, enable "Always-On VPN" under the community settings. This makes CT client to automatically connect on Windows logon. End-users will not be able to disconnect from VPN. If "Always-On VPN" is not enabled, then…
-
Thanks for bringing it up, this will be fixed in the September hotfix as well.
-
@Udana the latest Connect Tunnel clients are published on SonicWall website at https://www.sonicwall.com/products/remote-access/vpn-clients/. This macOS client supports Apple Silicon based Macs natively.
-
@Doug_Daniel This has been fixed in the upcoming 12.4.1 September hotfix. PS: If you would like to test it before, you can contact support and ask for test client (MCTSetup64-12.4.1.1000.exe) which is attached to our internal ticket (SMA1000-4358).